home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Columbia Kermit
/
kermit.zip
/
newsgroups
/
misc.19970104-19970326
/
000376_news@columbia.edu _Fri Mar 7 11:49:38 1997.msg
< prev
next >
Wrap
Internet Message Format
|
2020-01-01
|
2KB
Return-Path: <news@columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id LAA10003
for <kermit.misc@watsun.cc.columbia.edu>; Fri, 7 Mar 1997 11:49:37 -0500 (EST)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id LAA12400
for kermit.misc@watsun; Fri, 7 Mar 1997 11:49:35 -0500 (EST)
Path: news.columbia.edu!watsun.cc.columbia.edu!fdc
From: fdc@watsun.cc.columbia.edu (Frank da Cruz)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: Connection problem fixed
Date: 7 Mar 1997 16:49:33 GMT
Organization: Columbia University
Lines: 33
Message-ID: <5fpgut$skf$1@apakabar.cc.columbia.edu>
References: <E6oIHA.7q7@bigbird.telly.org>
NNTP-Posting-Host: watsun.cc.columbia.edu
Xref: news.columbia.edu comp.protocols.kermit.misc:6711
In article <E6oIHA.7q7@bigbird.telly.org>,
Evan Leibovitch <evan@bigbird.telly.org> wrote:
: The problems my system has had connecting to kermit.columbia.edu have
: been fixed. While nothing has changed at my end, connections are no
: longer refused.
:
: I wish to publicly thank Frank da Cruz and Fuat Baran at Columbia U.
: for their assistance in this matter.
:
Glad to help. The problem was evidently one of those that Joe D alluded
to in his posting. The Internet is becoming increasingly difficult to
manage and navigate, and problems like this have an ever-increasing number
of possible explanations.
Anybody who has trouble making *any* kind of connection should look over
Joe's brief message to get an idea of what might be up. It's worth
repeating here:
MAE-EAST and MAE-WEST Internet long distance carrier interchange
hubs are having a terrible time currently. That means lots of lost packets
and difficulty making connections. Your ISP may be having trouble too.
Those of you who run machines serving ftp, http, etc will note the
very large number of connections broken at the client end and left dangling.
Those use up limited server resources and take a while to die away.
... it is often wise to
check on connectivity in general, with ping and traceroute being two such
tools. Some sites do inverse lookups on callers to verify information, and
there are so many badly configured DNS servers that such lookups may fail
or take a long time to complete.
(end quote)
- Frank